home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
bbs_util
/
ftg110.zip
/
FILES2TG.DOC
< prev
next >
Wrap
Text File
|
1996-06-07
|
38KB
|
814 lines
|
| FILES2TG 1.10 documentation
|
| Full Featured files.bb? to Telegard 3.0 file-area converter.
|
| Copyright 1995,1996 by Dave Turner & THN Programming
| All rights reserved.
|
_____________________________
// PROGRAMME SYNOPSIS //
FILES2TG will read the DOS file FILES.BBS (or FILES.BB1 .. FILES.BB9)
in the download directory of all or a specified file area, and import
the files specified in the FILES.BB? into the Telegard 3 file record.
This utility is useful for persons using file distribution systems.
This product is named after Martin Pollard's FILES2TG.EXE which was
written for Telegard 2.7, and distributed as part of the Telegard 2.7
utilities package.
_____________________________
// SHAREWARE LEGALITIES //
This program has undergone many stages of testing by many people to
make it as reliable as possible. This program works for me and I
sincerely hope it works for you as well!
No warranties or responsibilities accompany this program. By using
this program, you agree that Dave Turner, THN Programming, and
members of the beta testing team, sites, and affiliate centres are not
liable for any destruction recurring from this programs use or misuse.
Further, you also agree not to pursue any legal actions or hold
accountable those mentioned above due to any damages . IF YOU DO NOT
AGREE, PLEASE DO NOT USE THIS PROGRAM.
FILES2TG is NOT public domain software. You are granted the right to
make as many copies of the standard release version as you wish
provided all files in the distribution archive remain intact, without
any changes or modifications. Hex edits, reverse engineering and any
other form of modification to FILES2TG (or any respective component)
is considered copyright infringement and legal action may be pursued.
This software was produced for Telegard 3.0/Gamma-4, and as such is
still in the stages of development. Version 1.10 is a total rewrite
of older versions. New wide-beta releases of FILES2TG v1.10 will be
made as bugs are fixed and/or features are implemented.
_____________________________
// PROGRAMME REQUIREMENTS //
FILES2TG.EXE is programmed to require the following:
HARDWARE:
■ AT-Compatible Bios,
■ 80+ Kilobytes of RAM. It is highly recommended that
FILES2TG.EXE never is run with less than 172 Kilobytes free
conventional RAM. More free memory makes file moving much
quicker.
■ A colour monitor capable of 80x25, 16/32c.
■ A hard drive (obviously)
SOFTWARE:
■ MS-DOS (or 100% compatible) Vsn 3.30 or better.
■ SHARE.EXE loaded {*}
■ Telegard 3.0/Gamma Bulletin Board operating System.
■ Files processor capable of producing a standard ASCII
FILES.BBS control file (ie: Allfix[R]).
_____________________________
// PROGRAMME INSTALLATION //
Installation of FILES2TG is quite simple since there is only ONE
executable file (FILES2TG.EXE), and vital runtime information is
gathered from the command-line and Telegard's data files.
If you use the "TELEGARD" environmental variable, FILES2TG will use
the directory specified in that variable. If you *do not* use this
variable FILES2TG will look for CONFIG.TG in: (1) the DOS search path
(2) current DOS directory.
FILES2TG *REQUIRES* a working directory for disk swapping (if needed),
file archive extractions and other miscellaneous tasks. FILES2TG will
use the pathspec specified by the DOS "TEMP" environmental variable.
If this variable does not exist, the directory FILES2TG is executed
form will be used.
FILES2TG will also search for the "FTGDUPE" environmental variable.
If found, the pathspec in "FTGDUPE" will be used for moving duplicate
files. The FTGDUPE environmental variable is ignored if the /M"???"
command-line argument is used.
Keeping the above in mind, place the FILES2TG.EXE in a directory where
it can access CONFIG.TG. Most people place FILES2TG.EXE in the main
Telegard directory (ie: C:\TG\).
_____________________________
// RUN-TIME DEFAULTS //
Although FILES2TG.EXE can run without the use of any command-line
arguments, it may be desirable to use command-line arguments to enable
some internal FILES2TG features.
By default (no command line parameters specified), FILES2TG will use
the following options/functions:
* Uses swapping to disk when shelling,
* Scan/Import into all non-cdrom Telegard file areas,
* Import files as "available, and hatch",
* Import missing files as offline entries,
* Move duplicate files,
* Use "FTG v1.10.wb?" as the file uploader string,
* Remove any FILES.BB? found after processing,
* Attempt to import a FILE_ID.DIZ/DESC.SDI from the archive; if
not available, the FILES.BB? description is used,
You can change these run time values by using any combination of
command line arguments (explained in the next section).
_____________________________
// COMMAND LINE PARAMETERS //
FILES2TG.EXE uses a command-line to pass arguments to define runtime
settings, such as duplicate file path, character stripping etc. The
following is a list and description of EACH valid command-line
argument (parameter).
-A"???" READ FROM FILES.BB? IN ALTERNATE PATHSPEC.
By default, FILES2TG will read from any FILES.BBS (or
FILES.BB1..FILES.BB9) located in the download path (file
storage pathspec) for each area.
Certain cd-rom distributors do not use the accepted file
(FILES.BB?) standard, thus resulting in compatibility
problems, since it is impossible to edit a file on
read-only media. The solution is to copy the offending
files.bb? into a temporary hard drive directory, and
edit it so that it becomes compatible.
Use this parameter if you wish to read from a files.bb?
located outside the area's file storage pathspec.
Place the complete (and valid) drive:directory\filespec
between the quotation marks. FILES2TG.EXE will attempt to
resolve the pathspec you supply. If the pathspec is
invalid, FILES2TG will terminate with a DOS ERRORLEVEL of
2. Do not include a trailing forward-slash.
This parameter only works when specified with the /B"???"
command-line argument. In other words, this option is
*not* valid on global tosses.
Example(s): FILES2TG.EXE /B"C:\TEMP!"
(* the above will cause FILES2TG to look
for a files.bb? in C:\TEMP! *)
-B"???" SCAN/IMPORT INTO FILE BASE ???.
By default, FILES2TG will scan and import all file areas
except those marked as cd-rom media (unless /C is used).
If you want to toss files in a particular file area, use
this parameter.
Place the complete (and valid) file area TAG name between
the quotation marks. FILES2TG will attempt to resolve the
tag name. If the area tag name is invalid, FILES2TG will
terminate with a DOS ERRORLEVEL of 2.
Example(s): FILES2TG.EXE /B"FIDOSDN"
(* the above will toss files in the area
with the tag name FIDOSDN *)
-C DO NOT SKIP (USE) CD-ROM FILE BASES.
By default, FILES2TG will not toss any FILES.BB? found in
areas designated as "cdrom media".
Use this argument if you wish to import FILES.BB? found on
cd-rom media. See section "IMPORTING CD AREAS"
Example(s): FILES2TG.EXE /C
-D PRESERVE (KEEP) ANY FILES.BB? FOUND AFTER USE.
By default, FILES2TG will purge any FILES.BB? files it
encounters during tossing, except those found in cd-media
designated bases.
If you wish the FILES.BB? file not to be removed from its
resting directory, use this parameter.
Example(s): FILES2TG.EXE /D
-E"???" CHANGE MEMORY SWAP LOCATION TO ??. 0=Disk 1=EMS 2=XMS
Whenever FILES2TG has to extract a FILE_ID.DIZ / DESC.SDI
from an archive, it will swap part of conventional memory
to another location. This gives the archive software
more RAM to operate with.
By default, FILES2TG will use the DISK swap shell. Disk
swapping is somewhat slower than EMS or XMS swapping, but
under certain environments, it may be the only option.
When you want FILES2TG to change swap type on-the-fly,
use the -E"???" parameter
If you want FILES2TG to preform it's memory swap to a
location other than the one defined in Telegard, use this
parameter.
Example(s): FILES2TG.EXE /E"1"
(* the above will swap to EMS *)
FILES2TG.EXE /E"2"
(* the above will swap to XMS *)
Memory errors can occur if EMS frame C800 is used for
BIOS shadowing, or when running under a multi-tasking
environment where not enough memory is allocated to the
task.
Also, when running FILES2TG while shelled from Telegard
or through Doorway, (or other shells that swaps to EMS),
it may be necessary to use XMS or DISK swapping.
-F DO NOT USE THE FILE'S FILE_ID.DIZ/DESC.SDI.
By default, FILES2TG will attempt to extract FILE_ID.DIZ
or DESC.SDI from any archive file TELEGARD can identify.
Descriptions from the FILE_ID.DIZ or DESC.SDI (if they
exist) are used in place of standard FILES.BB? extended
descriptions.
If you do not want FILES2TG to import the FILE_ID.DIZ or
DESC.SDI from a file archive, use this parameter.
This parameter is useful for people who use TIC file
processors which use the FILE_ID.DIZ or DESC.SDI from
archives as extended descriptions in the FILES.BB?
The actual process of swapping out and extracting a
FILE_ID.DIZ or DESC.SDI from archives can take a few
seconds.
Example(s): FILES2TG.EXE /F
-H DO NOT POST (SKIP) SYSTEM OPERATOR NOTIFICATION.
By default, FILES2TG will post a brief bullet-style
message to the system operator (the first record in the
user database) indicating the time and date FILES2TG was
last executed. This message is posted in the Telegard
SHORTMSG.DAT file. The message will be displayed during
a normal login or whenever the menucmd "LS" is issued.
If you do not want FILES2TG to post a short-message to
the system operator, use this command line argument.
Example(s): FILES2TG.EXE /H
-I IGNORE (DO NOT USE) EXTENDED DESCRIPTIONS.
By default, FILES2TG will take extended descriptions from
the FILES.BB? and use them in Telegard.
Use this argument if you wish to exclude extended (verbose)
descriptions.
Example(s): FILES2TG.EXE /I
-K CLEAN (NORMALIZE) DESCRIPTION CHARACTER CASINGS.
If you want FILES2TG to attempt casing normalization, use
this parameter. Casing normalization makes the first
character of each word an upper case letter, while making
any other characters lower case letters.
Numerical/high-ascii characters are ignored.
Example(s): FILES2TG.EXE /K
-L DO NOT UPLOAD MISSING FILES AS OFFLINE ENTRIES.
By default, FILES2TG will consider files which exist in
the FILES.BBS but not in DOS as offline, thus uploading
them as "offline entries". This is the opposite of how
previous versions did things.
If you want FILES2TG *not* to import files listed in the
the FILES.BB? but not found in DOS, use this parameter.
Example(s): FILES2TG.EXE /L
-M"???" CHANGE THE DIRECTORY FOR DUPE FILE MOVING TO ???.
By default, FILES2TG will attempt to move duplicate files
encountered unless they are on a cd-rom. You have *two*
options for specifying a directory (pathspec) for moving
duplicate files into.
The first option was described earlier. The "FTGDUPE"
DOS environmental variable can contain a pathspec for
moving duplicate files.
The second option involves using this argument to specify
a pathspec for moving files.
If the "FTGDUPE" and /M"???" are not provided, FILES2TG
will use the pathspec it was executed from. The /M"???"
will overide the "FTGDUPE" pathspec value.
Place the complete (and valid) drive:directory\ between
the quotation marks. FILES2TG will attempt to resolve the
pathspec you supply. If the pathspec is invalid, FILES2TG
will terminate with a DOS ERRORLEVEL of 2.
Example(s): FILES2TG.EXE /M"F:\DLS\FTGDUPES\"
FILES2TG.EXE /M"C:\BBS\DLOADS\FAILED"
-O UPDATE (REFRESH) ALL EXISTING FILES.
By default, FILES2TG will simply skip over any files
that already exist in the current area being scanned.
Since file distribution networks often re-hatch update
files using the same filename (ie: FILEBONE.NA), it may
be desirable to update the file's record to reflect the
new file size, points et al.
If you want to update existing files in the CURRENT area,
use this parameter.
Example(s): FILES2TG.EXE /O
-P"???" CHANGE DEFAULT FILE RECORD FLAGS TO ??.
By default, FILES2TG will import files as "available"
and "hatch". These are known as "file record flags". If
you wish to import files as "validated", "free download",
or "not download time check", use this parameter.
SYMBOL FLAG
F or f "freedl" flag
N or n "notimecheck" flag
V or v "validated" flag.
These symbols are used alone or in combination to tell
FILES2TG what you want in the file listing. Place the
symbols (listed above) between quotation marks; seperate
them with a colon -OR- semi-colon.
Example(s): FILES2TG.EXE /P"F:V"
(the above will upload files with the "freedl"
and "validated" flags.)
-R FILTER COLOUR OR MCI CODES FROM DESCRIPTIONS.
If you want to strip pipe/tilde colour codes found in the
file descriptions (if applicable), use this parameter.
This option will also remove ~xx Telegard MCI coding.
Example(s): FILES2TG.EXE /R
-S FILTER 8-BIT ASCII CHARACTERS FROM DESCRIPTIONS.
If you want to remove any characters classified as "high-
ascii", use this parameter.
This function will strip characters whose ordinate values
are from 001 to 031 and 127 to 255. Each non-printable
character striped is replaced with a space. For example:
replacing the non-printable characters in "┌───[FTG]───┐"
would result in: " [FTG] ".
Example(s): FILES2TG.EXE /S
-T USE IMPORT ACTIVITY TEXTUAL LOGGING.
FILES2TG offers both textual activity logging and textual
duplicate file logging. Textual activity logging is a
reasonably detailed log what FILES2TG does when tossing,
while textual duplicate file logging provides a semi-
detailed information on duplicate file encountered while
tossing.
Both these logs are stored in the Telegard logs pathspec.
Logs are limited only by available hard drive space.
Using the textual logging system will slow down average
tossing speed by a couple of seconds.
If you want FILES2TG to create and maintain these two log
files, use this parameter.
Example(s): FILES2TG.EXE /T
-U"???" CHANGE UPLOADER (UPLOADED BY) TO ???.
Telegard file areas have the ability to store the name or
alias of the user who uploaded a particular file. This is
known as the "uploader name" or simply "uploader".
By default, FILES2TG will place "FTG.EXE v1.10" as the
uploader when it imports files into Telegard. If you want
to specify a different uploader string, use this parameter.
Place the complete (and valid) uploader string of your
choice between the quotation marks.
Remember, spaces must be represented by the underscore
"_" character. Uploader name strings are limited to 35
characters
Example(s): FILES2TG.EXE /U"Software_Distribution_System"
FILES2TG.EXE -U"SysOp"
-V PURGE ANY DUPLICATE FILES ENCOUNTERED.
By default, all duplicate files encountered are moved from
the file area's directory into a duplicate file pathspec.
The duplicate file pathspec is defined using the "FTGDUPE"
DOS environmental variable, or the /M"???" command-line
argument.
Under high-traffic and/or low disk space conditions, it
may be desirable to purge any duplicate files rather than
store them. If you wish to PURGE any duplicate files found
during normal tossing of NON-CDROM bases, use this command-
line argument.
Example(s): FILES2TG.EXE /V
-W IGNORE (DO NOT CHECK) CD-ROM AREA/DISK LABELS.
By default, FILES2TG will check volume labels specified for
the file area against those on the actual cdrom. This is a
method of checking to see that cd-rom areas do not get
tossed together.
If you have reason NOT to preform volume/disk label checks,
use this parameter.
Example(s): FILES2TG.EXE /W
-X ENABLE FILE DESCRIPTION LONG LINE WRAPPING.
{ not fully implemented function }
By default, FILES2TG will *not* compensate for FILES.BB?
descriptions longer than 45 characters. Simply put, it will
ignore all characters after the 45th one. This also applies
to any FILE_ID.DIZ/DESC.SDI files.
There are times when it may be desirable to "wrap" long
descriptions. Use this command-line argument if you want
any long descriptions wrapped (as needed).
I am personally not in favor of this feature, therefore I
will not be going out of my way to finish it's final
implementation.
Example(s): FILES2TG.EXE /X
LIMITATIONS:
- Wrapping only applies to FILES.BB? descriptions,
- Line wrapping only works on descriptions shorter than
90 characters,
- There is no compensation for the "chainsaw" or "step"
effect,
- varied results appear when using MCI desc. codes,
-Z CHANNEL SCREEN WRITES THROUGH BIOS.
FILES2TG normally uses direct screen writes. Under certain
multitasker software such as DesqView this can cause screen
bleeding from one window to another. Most multitasking
software offer text/graphic virtualization, however, if
desired (as an alternative), you can instruct FILES2TG to
make all it's screen writes through your BIOS. This will
solve most screen-bleeding.
Example(s): FILES2TG.EXE /Z
Note, this option *will* slow the screen write rate quite
dramatically. This parameter does not appear on the valid
parameter list when you run FILES2TG.EXE /?
-? ACQUIRE PARAMETER HELP, EXIT
Like most command-line driven DOS programmes, FILES2TG has
an online argument listing with brief explanations. If you
require a reminder about parameters, use this command-line
argument.
Example(s): FILES2TG.EXE /?
FILES2TG exists with a DOS errorlevel of 1 after executing
this command.
If this command appears in combination with other command-
line parameters, it will take priority. This means you
cannot specify this parameter amoung other parameters.
FILES2TG will accept hyphenated parameters and oblique parameters. For
example, /C is the same as -C. Parameters can appear in any order, and
with exception to uploader name, casing is not important. If you pass
an illegal parameter, FILES2TG will terminate with a DOS errorlevel 1,
and display a brief message.
EXAMPLES:
1] To import files using description case cleaning, mci code stripping,
a duplicate directory of "D:\BADFILE" and an uploader "SDS: TG", key the
following: FILES2TG.EXE /K /R /M"D:\BADFILE\" /U"SDS:_TG"
2] To import files, refreshing when needed and using a duplicate file
directory of "E:\FTGDUPE", along with high ascii stripping, key the
following: FILES2TG.EXE -O -M"E:\FTGDUPE" -S
_______________________________
// WHEN TO RUN FILES2TG.EXE? //
You should run FILES2TG whenever your TIC file processor is executed
(if applicable). Run FILES2TG as you see fit.
______________________________
// MULTINODE CONSIDERATIONS //
Although file record locking and sharing routines are not implemented,
FILES2TG *can* be operated under some multinode environments. Ensure
that two copies of the programme never try to write to the same file
at the same time. It is best to ensure that FILES2TG doesn't get run
twice at the same time.
FILES2TG follows some multinode conventions observed in Telegard 3.0
such as keeping files open for brief (brief!) periods of time,
record tracking, and filemode checks.
Timeslices are not awarded in FILES2TG (why should they).
_____________________________
// ACTIVITY LOGGING //
A unique feature of FILES2TG is the textual activity logging system.
Previous versions featured a crude logging system. FILES2TG v1.10
now supports a more detailed, standardized textual logging system
that is still somewhat easy to understand.
Much like the previous version, log entries are created in blocks,
where each block of text represents when FILES2TG was booted. The
first part of the log block is the programme initialization record.
This block lists valuable information about runtime settings et al.
The initialization record (in the log) looks something like:
"----------- Friday, 04/05/1996, FILES2TG.EXE v1.10.b1
+ 01:51:41 Use cdrom bases...: No Clean desc casing : No
+ 01:51:41 Purge files.bb?...: No Use FILE_ID.DIZ...: Yes
+ 01:51:41 Keep any desc mci : Yes Keep hi-ascii desc: Yes
+ 01:51:41 Ignore extd desc : No Upload missing....: Yes
+ 01:51:41 Refresh existing..: No Memory swapping...: EMS
+ 01:51:41 SHARE.EXE detected: Yes DESQview detected : No (v0.00)
+ 01:51:41 Uploader string...: FTG.EXE v1.10.b1
----------- -----------------------------------------------------------"
Following the programme initialization record, are step-by-step notes,
that is, brief messages about stages of execution. These entries are
known as the "execution stage record", and can look something like:
"- 01:51:46 Using archive FILE_ID.DIZ for description
% 01:51:46 Wrote entry: VP10B003.ZIP, 649623 bytes, 63 pts.,
? 01:51:46 file does not exist: D:\TG\FILES\SYSOP\TGWAV101.ZIP
- 01:51:46 Making offline entry for: TGWAV101.ZIP
% 01:51:46 Wrote entry: TGWAV101.ZIP, 0 bytes, 0 pts.,"
It is important to note the usage of symbols (characters). The valid
logging symbol table is as follows:
SYMBOL MEANING
=================================================================
- (dash) A trivial message.
+ (plus) Programme initialization record designator.
% (percent) File import message.
? (question mark) Non-critical, Non-fatal error.
* (asterisk) Duplicate file encountered.
$ (dollar sign) Accounting/Transaction (ie moving, purging).
~ (tilde) Session information message.
The textual logging system is designed to provide the user and
programmer with information about stages in execution. Although it
may be somewhat strange to look at, it is not without use. As time
passes, the logging will be enhanced. At present 80% of all vital
modules / processes are logged.
_____________________________
// DUPLICATE FILE MOVING //
When FILES2TG.EXE moves a file into the duplicate directory (defined
by the -M"???" parameter, or "FTGDUPE" environmental variable), it
maintains a duplicate file tracking log, IF you enable the textual
logging system.
The duplicate file tracking log is a standard DOS text file. It is
written using the FILES.BBS format, with a few additions.
Just like textual activity logging, this log file ("FTGDUPE.LOG") is
placed in your Telegard logs directory (ie: C:\BBS\LOGS). This file
is limited only by available hard drive space.
______________________________
// IMPORTING CD AREAS //
Perhaps the most common usage of FILES2TG is importing file areas
contained on CD-ROM media. Although FILES2TG will not physically
create the areas based on cd-rom directories, it can toss files in
cd-rom FILES.BB? into Telegard.
There are numerous ways of importing files into cd-rom areas. The
most fail-safe way is by doing one area at a time. For example, say
the area "C11_BBS" has been created, and points to read-only media
in drive G. You're best bet would be:
FILES2TG.EXE /B"C11_BBS" /C /X /P"V"
Make sure the volume label for the area matches the cd-rom disk
label.
Times may exist when FILES2TG cannot work with the FILES.BB? used
on a cd-rom. This is 99.9% a result of the cd-rom publisher using a
non-standard FILES.BB? format. To overcome this problem, you will
need to copy the offending FILES.BB? to a hard drive directory and
edit it. TWO OUT OF THREE offending FILES.BB? have headers that do
not use semi-colon comment designators.
Lets say you copy an offending FILES.BB? to C:\TEMP!. After editing
it to compliance, you are ready to import the area. Lets assume the
area name is "C11_OS2" and we want to remove all 8-bit ascii and
import files as "free downloads". One possible command-line would
be:
FILES2TG.EXE /A"C:\TEMP!" /B"C11_OS2" /C /X /P"V;F"
__________________________________
// USING AN ALTERNATE FILES.BB? //
By default, FILES2TG will read from any FILES.BBS (or FILES.BB1
..FILES.BB9) located in the download path (file storage pathspec) for
each area.
Because there are many cd-rom distributors who use what I consider a
non-standard FILES.BB?, it may be necessary to read from a proper
files.bbs in order to achieve compatibility.
One can copy the offending FILES.BB? into a temporary area on a hard
drive, and modify it using any common textual editor.
The most common problems are headers in the files.bb? which do *not*
start with the commonly-accepted semi-colon comment character. There
are different adaptations of FILES.BB? standards for PCBoard, QBBS,
RBBS, and a few others. I have even seen CDs' distributed with non-
standard FILES.BB? filenames, such as "FILE.BBS", and "FILES.LST".
I do realize that this will be inconvenient for some, but who said
running a BBS was all fun and no work.
______________________________
// DESCRIPTION LINE WRAP //
Although a line-wrapping system was designed for this version of
FILES2TG, it is not yet fully implemented. Quite frankly, I think it
is more work than necessary. I will finish a simple line-wrap
mechanism sooner or later, but I doubt I will go to all the trouble
Tim Strike went to when he wrote Telegard's description line wrapping
mechanism.
_____________________________
// FUTURE CONSIDERATIONS //
A number of features have been slated for implementation within the
near future. Some of the features include:
i) file sharing/record locking routines
No deadline has been set for the implementation of these features.
_____________________________
// FILES.BBS CONVENTIONS //
FILES2TG.EXE uses the common FILES.BBS textual control file. Although
this version of FILES2TG allows for deviation from the proper file
format, it is still expected that certain conventions are followed.
Failure of this format will result in erroneous data entries.
DESCRIPTION LINE LENGTH:
Telegard supports description lines of up to 45 characters.
FILES2TG will stop reading a description line in the FILES.BBS
after it passes the 45 character limit. This applies for DIZ
imports too. MCI codes (`xx or |xx) count as 3 characters.
The 45 character limit is in accordance with the accepted
FILE_ID.DIZ standards.
EXTENDED DESCRIPTION CHARACTERS:
FILES2TG supports the popular extended description characters.
IF the extended description character used in the FILES.BBS is
not a member of [|, +, :, >, +, ' '], then the program will
probably not function properly.
Please note the following example:
FILE.ZIP This is a file with a two line xtended
|description using a valid xtended desc
|character [|, +, :, >, ' ']
FILE.ZIP This is a file with a two line xtended
description not using a valid xtended desc
description character, but spaces instead
The above two FILES.BB? record entries are acceptable and
will be parsed without error, however the following record
is *not* valid and will result in a parse error:
FILE.ZIP This is a file with a two line xtended
description not using a valid xtended desc char
or spaces instead. This will cause parse problems.
EXTENDED DESCRIPTION LENGTH:
New coding has enabled FILES2TG to accept up to 50 lines of
extended description (10 linked list nodes). Anything more
than 50 lines is simply ignored.
Although FILES2TG will import 50 lines of description,
Telegard will only read the first 26 lines of description.
There should be no real reason to describe a file using more
than 26 lines of extended description, however, the option
for some people is necessary.
BLANK LINES:
If the first few lines of the FILES.BB? are blank, FILES2TG
will continue reading until it can locate a valid FILES.BB?
record. If one cannot be found, FILES2TG will simply exit.
Blank lines between FILES.BB? records are now accepted. If a
a blank line is encountered between FILES.BB? records, it is
simply ignored.
HEADERS/FOOTERS:
Although headers and footers should not appear in any proper
FILES.BB? file, this version of FILES2TG will permit their
presence and simply ignore them provided *all* comment blocks
are designated with a semi-colon on the left most row & col.
FILES2TG was tested with the FILES.BBS found on the NightOwl v20 cdrom
and worked without flaw. FILES2TG was also tested using the FILES.BBS
created by Allfix[r] 4.32e.
_____________________________
// CREDIT WHERE IT BELONGS //
As with most projects, it always helps to have support. I would like
to thank all the members of The Telegard Team for beta testing this
project. Special thanks to Deanna Luke, Don Johnson & Mike Smith.
FILES2TG was first written by Martin J. Pollard as a part of the
Telegard 2.7 utilities package. FILES2TG.EXE v1.00 was taken from
Michael Bogden's IEBBS.EXE source code. FILES2TG.EXE v1.10 is totally
rewritten, from scratch using *no* previous coding.
"This product uses the SPAWNO routines by Ralf Brown to minimize memory
use while shelling to DOS and running other programs." (v4.10, 4/26/91)
"This product uses Tim Strike's FAST file index search coding." Many
thanks to Tim for his willingness to share.
All other products mentioned are copyright and or trademark of their
respective manufactures.
_____________________________
// PROGRAMME REGISTRATION //
This programme is *NOT* freeware, however a registration is *NOT*
required. Even though the programme is very flexible, It does
not warrant registration burdens. Use it as you please.
_____________________________
// CONTACTING THE AUTHOR //
If you have any problems or suggestions, you can contact the author
via the following means:
NETMAIL: Please address all netmail to "Dave Turner":
Fidonet -: 1:250/134
Telenet Canada -: 20:23/503
THNet -: 901:910/0
INTERNET EMAIL: ae907@torfree.net
BULLETIN BOARD: THN Systems Canada
(416) 255-2484
2400-14400 v.42bis
23hrs / 7 days a week
Zone Mail hour is 4:00am to 5:30am EST
POSTAL MAIL: THN Systems Canada
174 Sixth Street
Etobicoke, Ontario, Canada
M8V 3A5
We invite all comments and suggestions of a positive nature.
THANK YOU FOR CHOOSING FILES2TG
